-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
BUG: TypeError when doing equality comparison with Extension Dtype #44618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: TypeError when doing equality comparison with Extension Dtype #44618
Conversation
…rser (#44599) * BUG: Providing fix for GH#44366 * BUG: fix pre-commit run * BUG: adding other API changes for change of default argument * Rewriting if statement and adding test * BUG: changing pd.Series to Series to validate pre-commit hook * Removing the second whatsnew statement only to keep the bug fix one * BUG: simplifying the test with parser and parse_dates False #44366 * BUG: fixing pre-commit #44366
Hello @fotino21! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2021-12-05 10:54:23 UTC |
pandas/tests/dtypes/test_common.py
Outdated
@@ -391,6 +392,41 @@ def test_is_unsigned_integer_dtype(dtype): | |||
def test_is_not_unsigned_integer_dtype(dtype): | |||
assert not com.is_unsigned_integer_dtype(dtype) | |||
|
|||
def test_all_type_comparison(): | |||
assert pd.api.types.pandas_dtype("int_") == "int_" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls paramterize instead of writing out like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made the change you requested @jreback
…ests-for-dtype-comparisons added fix � �:Qa :qw
…no21/pandas into tests-for-dtype-comparisons
something when wrong |
@jreback I didn't understand |
@fotino21 you are updating a huge amount of code. make sure you are merging in master |
@jreback My changes are small and they are only in test_common file. What do i need to do for other commits by other people. And sorry for the inconvenience. This is my first contribution to a huge code base. |
@jreback I made it following this link: https://timonweb.com/misc/how-to-update-a-forked-repo-from-an-upstream-with-git-rebase-or-merge/ |
@fotino21 this has included lots of other changes u need to merge upstream/master |
How can i do that? I already based my master branch to upstream/master |
can you try
? |
In the second step, I only see this message: noop Rebase bc17343..bc17343 onto bc17343 (1 command)Commands:p, pick = use commitr, reword = use commit, but edit the commit messagee, edit = use commit, but stop for amendings, squash = use commit, but meld into previous commitf, fixup [-C | -c] = like "squash" but keep only the previouscommit's log message, unless -C is used, in which casekeep only this commit's message; -c is same as -C butopens the editorx, exec = run command (the rest of the line) using shellb, break = stop here (continue rebase later with 'git rebase --continue')d, drop = remove commitl, label = label current HEAD with a namet, reset = reset HEAD to a labelm, merge [-C | -c ] [# ]. create a merge commit using the original merge commit's. message (or the oneline, if no original merge commit was. specified); use -c to reword the commit messageThese lines can be re-ordered; they are executed from top to bottom.If you remove a line here THAT COMMIT WILL BE LOST.However, if you remove everything, the rebase will be aborted. |
🤔 to be honest I don't know, I can't even tell how you opened this PR as it doesn't appear to have come from a branch the other PR (#44840) does come from a branch, so maybe it's OK to continue there, then I can check it out locally if necessary |
closing in favor of #44840 @fotino21 ideallly we only have a single, original PR as it makes more work for maintaining. |
int64
withInt64
fails #43038 closes #xxxx